WebsydianSEI - Callback Point

AfterSessionIdentified

Type

Global callback point implemented by the WebsydianExpress runtime.

Note that changing the callback functions for a global callback point impacts all the sites.

When is the callback point called

The callback point is called for each request just after the session id has been determined based on the request or just after the session has been created.

How does the callback point influence later functionality

No direct influence.

Example of use

In a Windows WebsydianExpress implementation, where parts of the business application is executed on an iSeries, it can in some cases be beneficial to store the current session id in memory for the iSeries job servicing the request.

By entering a call to the function saving the session id in memory in this function you are certain that all requests are being handled and that the session id is available.

Abstract callback function

Inherit from Callback.WebServer.AfterSessionIdentified.AbstractCallbackFunction to create a callback function that can be called by this callback point.

CallbackInput

This local variable contains:

• APIFields.SessionIdentifiedInFunction - The session can be determined in three different ways:

1. If the session is part of the request - this will be done in the EventDispatcher function
2. If the session is created for a web request - this will be done in the CallFirstPageGenerator function
3. If the request is a service request, the session will be determined in the ServiceDispatcher

The field specifies the function that has determined the session and called the callback function.

• APIFields.SessionSurrogate - The unique identification of the current session

These fields will be populated automatically by the callback function. Use the values of these fields as you would use normal input fields.